The Mainframe Product must produce audit records containing information to establish where the events occurred.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-68245	SRG-APP-000097-MFP-000142	SV-82735r2_rule		Medium

Description
Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

Description

Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

STIG	Date
Mainframe Product Security Requirements Guide	2019-12-12

Details

Check Text ( C-68805r1_chk )
Examine installation and configuration settings. Verify data written to external security manager audit files and/or SMF records contain information that details where events occurred. If it does not, this is a finding.

Fix Text (F-74359r2_fix)
Configure the Mainframe Product audit records written to external security manager audit files and/or SMF records to contain information that details where the events occurred.